-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RelValMatrix fix mc for Ecal Alcareco #9298
Conversation
adding AlCaEle to 2015 RECO step for MC
A new Pull Request was created by @shervin86 for CMSSW_7_5_X. RelValMatrix fix mc for Ecal Alcareco It involves the following packages: Configuration/PyReleaseValidation @cmsbuild, @srimanob, @nclopezo, @boudoul, @franzoni can you please review it and eventually sign? Thanks. |
please test |
The tests are being triggered in jenkins. |
|
|
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_7_5_X IBs unless changes (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @smuzaffar |
+1 |
RelValMatrix fix mc for Ecal Alcareco
Dear all, |
adding AlCaEle to 2015 RECO step for MC:
ZEE, WE and TTbar samples have a RECOAlCaEle step instead of RECO, where the AlCa paths have been added.
The same for the corresponding 13TeV samples.
Ecal electron AlCa paths have been removed from the step4.
@franzoni @mmusich @diguida please double check eventual mistakes.
The following runTheMatrix have been tested:
runTheMatrix.py -j 5 -t 2 -l 25,26,29,1325,1326,1329
The results is:
25.0_TTbar+TTbar+DIGI+RECOAlCaEle+HARVEST+ALCATT Step0-PASSED Step1-PASSED Step2-PASSED Step3-PASSED Step4-PASSED - time date Wed May 27 18:33:36 2015-date Wed May 27 18:16:48 2015; exit: 0 0 0 0 0
26.0_WE+WE+DIGI+RECOAlCaEle+HARVEST Step0-PASSED Step1-PASSED Step2-PASSED Step3-PASSED - time date Wed May 27 18:32:42 2015-date Wed May 27 18:16:48 2015; exit: 0 0 0 0
29.0_ZEE+ZEE+DIGI+RECOAlCaEle+HARVEST Step0-PASSED Step1-PASSED Step2-PASSED Step3-PASSED - time date Wed May 27 18:32:37 2015-date Wed May 27 18:16:53 2015; exit: 0 0 0 0
1325.0_TTbar_13+TTbar_13+DIGIUP15+RECOUP15AlCaEle+HARVESTUP15+ALCATT+MINIAODMCUP15 Step0-PASSED Step1-PASSED Step2-PASSED Step3-PASSED Step4-FAILED Step5-NOTRUN - time date Wed May 27 18:37:59 2015-date Wed May 27 18:16:56 2015; exit: 0 0 0 0 16640 0
1326.0_WE_13+WE_13+DIGIUP15+RECOUP15AlCaEle+HARVESTUP15+MINIAODMCUP15 Step0-PASSED Step1-PASSED Step2-PASSED Step3-PASSED Step4-PASSED - time date Wed May 27 18:35:27 2015-date Wed May 27 18:16:58 2015; exit: 0 0 0 0 0
1329.0_ZEE_13+ZEE_13+DIGIUP15+RECOUP15AlCaEle+HARVESTUP15+MINIAODMCUP15 Step0-PASSED Step1-PASSED Step2-PASSED Step3-PASSED Step4-PASSED - time date Wed May 27 18:47:49 2015-date Wed May 27 18:32:40 2015; exit: 0 0 0 0 0
6 6 6 6 3 0 tests passed, 0 0 0 0 1 0 failed
The AlCaTT is failing as you can see:
----- Begin Fatal Exception 27-May-2015 18:37:38 CEST-----------------------
An exception of category 'ProductNotFound' occurred while
[0] Processing run: 1 lumi: 1 event: 8
[1] Running path 'pathALCARECOHcalCalIsoTrk'
[2] Calling event method for module AlCaIsoTracksProducer/'IsoProd'
Exception Message:
Principal::getByToken: Found zero products matching all criteria
Looking for type: trigger::TriggerFilterObjectWithRefs
Looking for module label: hltL1sL1SingleJet68
Looking for productInstanceName:
Additional Info:
[a] If you wish to continue processing events after a ProductNotFound exception,
add "SkipEvent = cms.untracked.vstring('ProductNotFound')" to the "options" PSet in the configuration.
The issue is not solved. Looking at the RelVal I spotted an error that I corrected in the last commit:
I have added an ALCATT for 13TeV and replaced in TTbarUp15 the ALCATT with the newly created ALCATTUp15 (I don't know who are the consumer of that and why this has not been spotted before)